home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950528-19950726
/
000010_news@columbia.edu_Tue May 30 20:06:17 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA16439
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 31 May 1995 06:42:28 -0400
Received: by apakabar.cc.columbia.edu id AA27039
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 31 May 1995 06:42:25 -0400
Path: news.columbia.edu!panix!news.mathworks.com!gatech!concert!ais.com!bruce
From: bruce@ais.com
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit-32 (VAX) problems??
Message-Id: <1995May31.010617.7767@ais.com>
Date: 31 May 95 01:06:17 EST
References: <D9CztC.Cu6@inter.NL.net>
Organization: Applied Information Systems, Chapel Hill, NC
Lines: 46
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <D9CztC.Cu6@inter.NL.net>, avdpeijl@inter.NL.net writes:
> Hello everybody,
>
> I would like to upgrade Kermit on my VAX. At the moment I have a stone-aged
> version of Kermit-32 (1984 or something like that). With MS-Kermit 3.14 I
> tried to upload some programms to the VAX with settings like:
> - packetlength 94
> - no linking shift (or something simular)
> - set block 1-bit (also tried 2-bit)
> - file type binary (of course)
>
> The uploads went fine. I reached a 23% troughput at a 9600 bps line (VT220),
> found no particular errors (only at the end Kermit-32 complained about bad
> packets).
>
> When I run the program, I get:
> "error activating image zip.exe" and "image header description length is
> invalid" (in this example I uploaded unzip.exe for VAX/VMS, 54k).
Try doing a SET FILE TYPE FIXED in Kermit-32 before you upload the
zip.exe file. The default file type has varying-length records which
are not allowed for executable images. Most likely the other settings
had nothing to do with your problem; you will however get more reliable
transfers if you set BLOCK to 2 or 3 (this is the block check algorithm,
and 1 is very minimal but usually adequate for short packets. You would
still be advised to use one of the more advanced block check methods
that are less subject to letting bad data through). Locking shifts are
purely a transfer speed issue; I don't know if such an old version of
Kermit-32 would support them (in fact I'm unsure offhand if _any_ version
of Kermit-32 supported them), but they are certainly not your problem.
Note that you need to have been very careful about transferring the
zip.exe file to the PC in the first place. It needs to be an exact
binary copy of the file on the VAX (without the implied record boundaries
every 512 bytes, of course). Many methods of transferring the file will
cause it to be corrupted: for example, if its path included being copied
as a text file by Kermit or FTP, then it may have extra CR/LF pairs added
or existing CRs or LFs in the file modified into CR/LF pairs. This will
make the file unuseable as an executable file under VMS.
C-Kermit for VMS is an enormous improvement over Kermit-32 - you should
try to get hold of it as soon as possible.
Good luck,
Bruce C. Wright